Plugin/Theme Registry or Website Update

Thank you for contributing to the RusherHacks Plugin Collection!
Please fill out the details below to help keep review quick and clean.

Type of Change

• Plugin/theme registry update
• Plugin/theme search website update
• Both

Summary of Changes

Before You Submit

Routine plugin/theme update maintenance is handled automatically by our scripts.

You do not need to open a PR just to update:

• latest_release_tag
• jar_url
• generated markdown files
• generated JSON files
• other automation-managed output files

PRs are mainly for:

• adding a new plugin or theme
• correcting metadata the automation cannot determine
• updating descriptions, screenshots, creator info, version support, or structure in data/plugins-and-themes.yml
• updating the plugin/theme search website

Checklist

• I updated only the relevant files for this PR
• If this is a registry update, I updated data/plugins-and-themes.yml and, if needed, related Assets/** files for screenshots
• If this is a website update, I changed only the relevant website files
• All required fields are present and correctly formatted
• YAML syntax is valid (quotes, spacing, indentation), if applicable
• GitHub repo is public and accessible, if applicable
• MC versions and release info are accurate, if applicable
• This PR is not only for auto-managed release, jar, or generated file updates

When a PR is opened or updated, GitHub Actions automatically validates the PR changes and the YAML file.
After YAML changes are merged into main, generated markdown and JSON output files are updated automatically.
If the PR fails checks, the error message should help show what needs to be fixed.

Quick Field Reference

• name → Display name of the plugin/theme
• repo → GitHub repo in owner/repo format
• description → One-line summary
• creator → Object with:
  • name: Author name
  • url: Author profile URL
  • avatar: Author avatar URL (for example, GitHub .png?size=20)
• latest_release_tag → Latest GitHub release tag, if applicable
• screenshots → List of screenshots with:
  • url: Path to image in ./Assets/... or valid hosted image
  • alt: Short description
  • width: Optional width in pixels
• is_core → true if it is a core plugin, otherwise false
• mc_versions → Supported versions (range like 1.20.1-1.21.4 or list)
• jar_url → Direct link to the .jar release asset, if applicable
• added_at → Date added to the registry
• updated_at → Auto-managed update date

Additional Notes (optional)